Secure authentication of a user

ABSTRACT

A device detects a communication involving a user associated with an account and a service representative, and sends, to a user device associated with the account, an authentication notification that causes the user device to display an authentication field for the user. The device sends, to a service representative device associated with the service representative, a message that indicates that the service representative is to request, via the communication, the user to enter personal information associated with the user into the authentication field, where the user device is configured to generate a first authentication code based on a user input received from the user device in the authentication field. The device generates a second authentication code based on personal information associated with the account from a data structure, receives the first authentication code, and performs an action based on the first authentication code and the second authentication code.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/544,244, filed Aug. 19, 2019 (now U.S. Pat. No. 11,356,439), which isa continuation of U.S. patent application Ser. No. 16/239,149, filedJan. 3, 2019 (now U.S. Pat. No. 10,389,708), the contents of which areincorporated herein by reference in their entireties.

BACKGROUND

An authentication process may be performed to verify an identity of anindividual. For example, when the individual contacts a call center ofan entity regarding an account maintained by the entity, the call centermay authenticate the individual to verify that the user is associatedwith the account and not a fraudulent actor attempting to gain unlawfulaccess to the account.

SUMMARY

According to some implementations, a method may include detecting acommunication to a call service center, wherein the communication isbetween a user device associated with a user, and a servicerepresentative device associated with the call service center. Themethod may include providing, to the user device, an authenticationnotification to request a first authentication code, wherein theauthentication notification causes an authentication application tolaunch on the user device, wherein the authentication applicationgenerates the first authentication code by hashing a user input with atime-sensitive code, and wherein the user input is received by theauthentication application from the user via a user interface of theuser device in association with a request that the user provide aplurality of pieces of personal information. The method may includereceiving the first authentication code, and generating a secondauthentication code, wherein generating the second authentication codecomprises obtaining the plurality of pieces of personal information,corresponding to the authentication request, from a data structure, andhashing the plurality of pieces of personal information with thetime-sensitive code to generate the second authentication code. Themethod may include performing an action based on whether the firstauthentication code matches the second authentication code.

According to some implementations, a device may include one or morememories, and one or more processors, communicatively coupled to the oneor more memories, configured to detect a communication involving aservice representative and a user associated with an account, and tosend an authentication notification to a user device that is associatedwith the account, wherein the authentication notification causes theuser device to display, via a user interface of the user device, anauthentication field for the user. The one or more processors may send amessage to a service representative device that is associated with theservice representative, wherein the message indicates that the servicerepresentative is to request, via the communication, the user to enterpersonal information associated with the user into the authenticationfield, wherein the user device is configured to generate a firstauthentication code based on a user input received, via the userinterface of the user device, in the authentication field. The one ormore processors may generate a second authentication code based onpersonal information associated with the account from a data structure.The one or more processors may receive the first authentication code,and may perform an action based on the first authentication code and thesecond authentication code.

According to some implementations, a non-transitory computer-readablemedium storing one or more instructions that, when executed by one ormore processors, cause the one or more processors to identify an accountassociated with a user via a first communication interface associatedwith a service platform, and to obtain personal information associatedwith the account. The one or more instructions may cause the one or moreprocessors to send an authentication notification to a user deviceassociated with the user, wherein the authentication notificationprompts the user to enter the personal information via a user interfaceof the user device to permit the user device to generate a firstauthentication code. The one or more instructions may cause the one ormore processors to receive the first authentication code from the userdevice, to compare the first authentication code and a secondauthentication code generated based on the obtained personalinformation, and to perform an action based on the first authenticationcode and the second authentication code.

According to some implementations, a method may include detecting acommunication with a user device of a user. The method may includeproviding, to the user device, an authentication request, wherein therequest causes an authentication function to be presented on the userdevice, wherein the authentication function is configured to generate afirst authentication code by hashing a user input received inassociation with a request for a piece of personal information of auser, and wherein the user input is received via a user interface of theuser device. The method may include receiving the first authenticationcode from the user device, and generating a second authentication code,wherein generating the second authentication code comprises obtainingthe piece of personal information from a data structure, and hashing thepiece of personal information to generate the second authenticationcode. The method may include authenticating the user based on the firstauthentication code matching the second authentication code.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIGS. 4-7 are flow charts of example processes for secure authenticationof a user.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

In many instances, when a user contacts a service representative of anentity regarding an account maintained by the entity (e.g., a memberaccount, a financial account, and/or the like), the servicerepresentative authenticates the user to verify that the user isassociated with the account and not a fraudulent actor attempting togain unlawful access to the account. In such cases, to authenticate theuser, the service representative may ask the user to verifyauthentication information (e.g., personal information associated withthe account that was previously provided to the entity, accountinformation associated with the account, and/or the like). If the userprovides authentication information that matches the authenticationinformation of the account, the service representative may authenticatethe user and enable the user to access information associated with theaccount and/or perform an action associated with the account.

In many instances, such an authentication process takes place over aphone call and/or via a chat interface (e.g., an instant messaginginterface). Accordingly, for the user to be authenticated, the userneeds to share the authentication information over the phone call and/orthrough the chat interface. Therefore, that authentication informationcan relatively easily be acquired by any individual that is within rangeof hearing the user communicate the authentication information over thephone and/or by a hacker who has hacked the chat interface tofraudulently gain access to the authentication information. Furthermore,if the service representative has fraudulent intentions, the servicerepresentative may acquire such personal information and/or accountinformation for fraudulent use (e.g., to gain access to the user'saccount). Therefore, using previous techniques for authentication via aservice representative, a user's account and/or personal information maybe put at risk due, for example, to authentication information that maybe used to access the account being available to potentially fraudulentindividuals.

Some implementations described herein provide a more secure system forsecure authentication of a user. As described herein, the user may becommunicating via a communication interface (e.g., a phone call, a chatinterface, and/or the like) with a service platform (e.g., a call centerplatform) to initiate a communication with a service representative.Additionally, or alternatively, the user may be in communication with aservice representative via the communication interface (e.g., theservice platform forwarded the call to the service representative and/orengaged the service representative in a chat with the user). Accordingto some implementations, an authentication platform is configured toauthenticate the user without the user needing to communicate sensitiveauthentication information, such as sensitive personal information orsensitive account information, to the service platform or the servicerepresentative.

As described herein, after a user is identified via the communicationinterface (e.g., based on a caller identification (caller ID), enteringidentification information (e.g., account information, an identificationnumber, and/or the like)), an authentication platform may request a userto provide authentication information via a user device (e.g., via anapplication of the user device, a message provided to the user device,and/or the like) associated with the user. The authenticationinformation, which may include personal information and/or accountinformation that is to be kept private, may then be used to generate anauthentication code (e.g., via a hash function) that can be provided toauthenticate the user. The authentication code may be compared to anauthentication code that is generated by the authentication platformusing authentication information, associated with the account, thatcorresponds to the authentication information requested from the user.The authentication platform and/or service representative (e.g., if theauthentication codes are provided to the service representative) maycompare the authentication codes to determine if the authenticationcodes match. Accordingly, the authentication platform and/or servicerepresentative may authenticate the user, in real-time, if the codes domatch, and not authenticate the user, in real-time, if theauthentication codes do not match.

Accordingly, rather than the individual having to share personalinformation and/or account information with the service representative(e.g., aloud via a phone call, through a chat interface that issusceptible to being hacked, and/or the like), the user may discreetlyenter the personal information and/or account information into a userdevice, which is then used to generate an authentication code. In thisway, the authentication code is communicated to the servicerepresentative (and/or authentication platform) such that the personalinformation and/or account information is not at risk of being obtainedor acquired by a potentially fraudulent individual (i.e., an individualengaged in fraudulent activity). Accordingly, some implementationsdescribed herein may prevent fraudulent activity involving a user'saccount that may result from a fraudulent individual obtaining personalinformation and/or account information from the user while the user iscommunicating with a service platform and/or with a servicerepresentative. Therefore, the authentication platform, as describedherein, may conserve computing resources (e.g., processing resources,memory resources, power resources, and/or the like) and/or networkresources involved in correcting any fraudulent activity that would havebeen allowed without the use of the authentication platform describedherein. Furthermore, the authentication platform, as described herein,enables improved authentication of a user that is communicating with aservice provider and/or service representative, relative to previoustechniques.

In some implementations, the authentication platform may authenticatethe user before the user communicates with the service representative(e.g., before the service representative answers a phone call or entersthe chat interface). For example, the authentication platform mayidentify the user via the communication interface and request the userto enter, via a user device and/or an application of the user device, auser input associated with requested personal information and/or accountinformation. As described herein, the user device may generate anauthentication code based on the user input and provide theauthentication code to the authentication platform. Accordingly, theauthentication platform may receive the authentication code and performan authentication process by comparing the authentication code to anauthentication code generated by the authentication platform usingcorresponding personal information and/or account information that wasrequested from the user via the user device. If the authentication codesmatch, the authentication platform may permit the user to engage incommunication with the service representative via the communicationinterface.

In this way, several different stages of a process for authenticating auser in communication with a service platform and/or servicerepresentative are automated, which may remove human subjectivity andwaste from the process, and which may improve speed and efficiency ofthe process and conserve computing resources (e.g., processor resources,memory resources, and/or the like). Furthermore, some implementationsdescribed herein use a rigorous, computerized process to perform tasksor activities that were not previously performed. For example,previously, there did not exist a technique to detect a communicationwith a user; provide an authentication request, to a user device of theuser, that causes an authentication function to be performed on the userdevice to generate an authentication code based on a user input from theuser; receive the authentication code and compare the authenticationcode to another authentication code generated based on correspondinginformation that is associated with the user input; and authenticateand/or enable authentication of the user based on the two authenticationcodes. Accordingly, computing resources associated with a servicerepresentative authenticating a user via a communication interface, asdescribed herein, are conserved. Moreover, automating the process forauthenticating the user (e.g., before the user is connected with aservice representative), as described herein, conserves computingresources (e.g., processor resources, memory resources, and/or the like)that would otherwise be wasted by the service representative requestingauthentication information via the communication interface, receivingauthentication information via the communication interface, andauthenticating the user. Furthermore, the authentication platformprovides an improved user experience associated with authenticating theuser in that the user is not placed in an uncomfortable position ofproviding personal information and/or account information to a servicerepresentative and/or in front of other individuals that may hear thepersonal information and/or account information. Accordingly, the usermay be more comfortable knowing that personal information of the user isnot subject to eavesdropping and/or hacking, and the entity may, thus,gain more customers and/or may satisfy their customers by protecting thepersonal information.

FIGS. 1A-1C are diagrams of an example implementation 100 describedherein. Example implementation 100 includes a user device, a servicerepresentative device, a service platform, and an authenticationplatform. As described herein, the service representative device, theservice platform, and/or the authentication platform may be associatedwith an entity, such as an entity that provides a service to a user ofexample implementation 100.

As shown in FIG. 1A, and by reference number 110, the user engages in acommunication with the service platform (e.g., to speak with a servicerepresentative). In some implementations, the user may engage in thecommunication via the user device and/or some other device (e.g.,another user device, a telephone, such as a landline telephone, anonline portal, and/or the like). As described herein, the communicationmay include speaking through a phone call, sending instant messages,email messages, text messages, and/or the like. Accordingly, thecommunication may be performed via a communication interface, such asthe phone, a chat interface (e.g., used to exchange (send and/orreceive) the instant messages), and/or the like. Therefore, thecommunication may involve real-time communication between the user andthe service platform and/or between the user and the servicerepresentative.

In some implementations, the user initiates the communication with theservice platform. For example, the user may contact (e.g., via a phonecall, a chat interface, and/or the like) the service platform and/orservice representative to discuss a matter associated with an account.More specifically, the user may contact the service platform and/orservice representative to discuss a billing matter, engage in atransaction (e.g., to purchase a product, to pay for a service, and/orthe like), apply to engage in a transaction (e.g., apply for a loan,apply to lease a product, and/or the like), and/or the like. In someimplementations, the service platform and/or service representative mayinitiate the communication with the user. For example, the serviceplatform and/or service representative may contact the user to verifyinformation associated with the account, to verify a transactioninvolving the account, to provide information associated with theaccount, to request payment associated with the account, and/or thelike.

As described herein, the account is associated with the entity in thatthe account may be used (e.g., by an authorized user) to interact withthe entity (e.g., provide information to the entity, perform one or moreactions involving the entity, such as make a payment to the entity orengage in a transaction with the entity, and/or the like). As describedherein, the authentication platform performs an authentication processto verify that the user is associated with the account, in order toprevent fraudulent access to the account (e.g., by an unauthorizeduser). Accordingly, if the user is an authorized user of the account,the account may be considered an account of the user.

In some implementations, the service platform may perform one or moreoperations to identify the user (e.g., when the user initiates thecommunication). For example, the service platform may use a caller IDprocess to identify the user (e.g., by matching a phone number to aphone number associated with the account). Additionally, oralternatively, the service platform may prompt the user (e.g., via anautomated call answering system and/or an automated informationgathering system of a chat interface, and/or the like) to provideidentification information associated with the user (e.g., a name, anidentification number, an account number, and/or the like) via thecommunication interface, e.g., a microphone, touchscreen interface,keypad, or the like. In such cases, the user may be able to speak and/orprovide the identification information via a user interface of the userdevice. Additionally, or alternatively, the service platform mayidentify the user based on the communication being initiated from anaccount associated with the entity. For example, the user may open achat interface after the user logs in to a webpage or application thathosts the chat interface. In such cases, identification informationassociated with the account from which the user accessed the chatinterface may be used to identify the user. Accordingly, the serviceplatform may obtain identification information associated with the userand/or identification information associated with the account, andprovide such identification information to the authentication platformto permit authentication of the user as described herein.

In some implementations, the service platform may request the user toindicate a purpose for the communication (e.g., to pay a bill, todispute a bill, to engage in a transaction, to apply for a loan, toorder a service and/or good, and/or the like). The service platform mayuse any suitable technique to determine the purpose of the call, such asnatural language processing of speech and/or text from the user receivedvia the communication interface, from an automated call answering systemthat prompts the user to provide the purpose of the call through a userinput, from an automated information gathering system that prompts theuser to select a purpose of the communication, and/or the like.

In some implementations, the authentication platform may detect thecommunication between the user and the service platform and/or betweenthe user and the service representative. For example, the authenticationplatform may detect that a communication interface has been opened withthe service platform and/or the service representative. Additionally, oralternatively, the authentication platform may detect the communicationbased on receiving identification information associated with the user.In some implementations, the authentication platform may suspendcommunication between the user and the service representative until theuser is authenticated according to one or more of the implementationsdescribed herein. In this way, the user may be prevented fromcommunicating with the service representative until the user isauthenticated, to ensure that the user is not an unauthorized user(e.g., a fraudulent individual) and/or does not receive fraudulentaccess to an account of a customer of the entity via the communicationwith the service representative.

Accordingly, the user may engage in a communication with the serviceplatform and/or the service representative to permit the user to beauthenticated via an authentication process, as described herein. Insome implementations, the authentication platform may detect thecommunication in order to permit the authentication platform to obtainidentification information associated with the user and/or perform anauthentication process as described herein. Additionally, oralternatively, the service representative may obtain the identificationinformation and/or cause the authentication platform to initiate theauthentication process (e.g., based on receiving the identificationinformation from the user).

As further shown in FIG. 1A, and by reference number 120, theauthentication platform obtains the identification informationassociated with the user, in order to initiate the authenticationprocess. For example, the authentication platform may obtain theidentification information from the service platform based on responsesfrom the user provided to the automated answering system and/or theautomated information gathering system of the service platform.Accordingly, the service platform may be configured to provideidentification information to the authentication platform while the useris in communication with the service platform, to permit theauthentication platform to authenticate the user.

In some implementations, the service representative may be engaged inthe communication with the user and/or may obtain the identificationinformation to initiate the authentication process. For example, theservice representative may request the user to provide suchidentification information to the service representative via thecommunication, to permit the service representative to identify the userand/or to identify the account involved in the communication. In suchcases, the service representative may provide the identificationinformation to the authentication platform to permit the authenticationplatform to authenticate the user as described herein.

In this way, the authentication platform may obtain identificationinformation of the user to permit the authentication platform to send anauthentication notification and/or an authentication request to a userdevice of the user to initiate an authentication process as describedherein.

As further shown in FIG. 1A, and by reference number 130, theauthentication platform requests the user to provide personalinformation to the user device to authenticate the user. Although someimplementations described herein discuss using personal information,additionally, or alternatively, any other type of authenticationinformation (e.g., account information, passwords, and/or the like) maybe used to authenticate a user as described herein. As described herein,the personal information may be used to generate an authentication codethat the authentication platform uses to authenticate the user, withoutthe user needing to share the personal information via the communicationbetween the user and the service platform and/or via the communicationbetween the user and the service representative.

As used herein, personal information may be any information associatedwith a customer (e.g., the user, if the user is associated with thepersonal information) of the entity that may have been provided to theentity and/or obtained by the entity. For example, the personalinformation may have been provided, by the customer (e.g., the user), tothe entity in a previous communication, when registering the account,when updating the personal information in an account maintained by theentity, when engaging in a transaction with the entity, when providingthe personal information for authentication purposes, and/or the like.More specifically, personal information may include a name, anidentification number (e.g., a government-issued identification number,an account number, a member identification number associated with theentity, and/or the like), a date of birth, an address or locationinformation, a password, an answer to an authentication question, afavorite item, a relative's name, a friend's name, and/or the like.Additionally, or alternatively, the personal information may beinformation associated with one or more transactions associated with theaccount (e.g., when a transaction was made, what the transactioninvolved, and/or the like). In some implementations, the personalinformation may be stored in a data structure (e.g., a database ofcustomer information and/or customer accounts) in association with theaccount (e.g., as information of the account). Accordingly, the personalinformation, associated with an authorized user of the account, may bestored in a data structure prior to the user engaging in thecommunication with the service platform and/or the servicerepresentative. Therefore, if the user is an authorized user, the usermay recall, via a user input device, the personal information that waspreviously provided to the entity to permit the authentication platformto authenticate the user.

In some implementations, the authentication platform may access and/orobtain the personal information (e.g., from the data structure)associated with the account to determine which personal information canbe requested from the user to authenticate the user. For example, basedon receiving the identification information, the authentication platformmay access the account (e.g., in the data structure) to identifypersonal information that was provided to the entity. Further, theauthentication platform may select which personal information is to beused to authenticate the user. Accordingly, the authentication platformmay request personal information that is available to authenticate theuser. In other words, the authentication platform may not request theuser to provide personal information that cannot be verified by theauthentication platform because the personal information was notpreviously provided or available to the entity. In some implementations,the authentication platform may randomly select which personalinformation is to be used to authenticate the user. Additionally, oralternatively, the authentication platform may select the personalinformation and/or an amount of the personal information (e.g., aquantity of pieces of the personal information) that is to be used toauthenticate the user based on one or more characteristics of the user,one or more characteristics of the communication, and/or the like. Forexample, the authentication platform (e.g., from natural languageprocessing and/or information received from the service platform) maydetermine the purpose of the communication, and, based on the purpose ofthe communication, select a quantity of pieces of personal informationand/or select which pieces of personal information are to be used toauthenticate the user. For example, if the user is calling to pay abill, the authentication platform may request that only one piece ofpersonal information (e.g., information printed on the bill) beprovided, and if the user is calling to engage in a transaction and/ororder goods or services, the authentication platform may request thatthe user provide more than one piece of personal information.Additionally, or alternatively, if the user is calling to pay a bill,the authentication platform may request that the user provides theuser's date of birth or name (e.g., personal information that may bemore readily available or easy for the user to input), and if the useris calling to engage in a transaction, the authentication platform may(alternatively or additionally) request the user to verify a relative'sname, a friend's name, a favorite hobby of the user, and/or the like(e.g., personal information that is less likely to be available to anunauthorized user).

As described herein, the authentication platform may send anauthentication notification to request the user to provide the personalinformation (e.g., via an authentication function of the user device).For example, the authentication notification may cause the user deviceto display, via a user interface of the user device, an authenticationfield to permit the user to enter the personal information. In someimplementations, the authentication notification may provide a messageand/or indication to the user to notify the user which personalinformation is to be provided and/or entered into the field. In someimplementations, the authentication notification is received by the userdevice via an application installed on the user device. The applicationmay be an authentication application and/or an application or browserplug-in that is associated with the entity (e.g., an application thatpermits the user to access the user's account with the entity, anapplication to perform one or more operations associated with theaccount (e.g., pay a bill, engage in a transaction, submit anapplication for a service offered by the entity, and/or the like),and/or the like). Accordingly, the authentication field may be a fieldof the application that the user may access by opening the applicationvia the user device.

In some implementations, the user may need to log in to the application(e.g., using login information associated with the account, logininformation associated with the user device, a biometric of the user,and/or the like). In some implementations, the account may be registeredto the application. In such cases, the user logging into the applicationmay serve as an additional factor in the authentication platformauthenticating the user. In some implementations, the authenticationnotification may provide instructions and/or prompt the user to downloadand install the application to permit the authentication platform toauthenticate the user (e.g., if the application is not installed on theuser device prior to the authentication platform sending theauthentication notification).

In some implementations, the service representative may request the userto enter the personal information to authenticate the user. For example,the service representative may cause the user device to prompt the userto enter the personal information (e.g., by sending, from the servicerepresentative device, an authentication notification). Additionally, oralternatively, the service representative may request the user, via thecommunication, to navigate to the authentication field and input thepersonal information (e.g., a specific piece of personal information).Accordingly, in some implementations, the user device (and/or theapplication) provides the authentication code based on a requestreceived from the service representative device (e.g., the servicerepresentative requests the user device and/or application toauthenticate the user) and/or receiving a user input in anauthentication field of the user device and/or application.

In some implementations, the authentication notification may be sent viaa separate communication interface from the communication interface usedfor the communication between the user and the service platform and/orbetween the user and the service representative. For example, while theuser may communicate with the service platform and/or the servicerepresentative via a phone call and/or a chat interface, theauthentication notification may be received via a messaging protocolassociated with the application of the user device, via a separatenetwork, and/or the like.

In this way, the authentication platform may request a user to enterpersonal information and/or cause a user device to generate anauthentication code based on a user input received in association withthe request for the user input. The authentication platform may use theauthentication code generated based on the user input to authenticatethe user by comparing the authentication code to an authentication codegenerated by the authentication platform based on the personalinformation of the user in the data structure.

As shown in FIG. 1B, and by reference number 140 a, the authenticationplatform may receive the authentication code that was generated based onthe user input from the user that was provided in response to therequest for the personal information. Accordingly, the user input may bethe requested personal information if the user (presumably an authorizeduser) knows the personal information, or the user input may beinformation that is not the requested personal information because theuser (presumably an unauthorized user) did not know the personalinformation that was requested.

As described herein, based on receiving the authentication notification,the user device may generate the authentication code based on the userinput received from the user in response to the request for the personalinformation. Accordingly, the authentication notification may serve asan authentication request that causes an authentication function to bepresented on the user device. For example, the authentication functionmay be launched independently from the application and/or launchedwithin or by the application. In some implementations, theauthentication function may cause the application to be launched (e.g.,when the user unlocks the a mobile device and/or accesses a userinterface of the mobile device) on the user device. As described herein,the authentication function may be configured to generate anauthentication code based on the user input (which may be the requestedpersonal information) that is provided by the user. For example, theauthentication function may hash the user input to generate theauthentication code and/or use the user input in a hash function (e.g.,as an input to the hash function) to hash a time-sensitive code (e.g., atime-sensitive code provided by the authentication platform) with theuser input to generate the authentication code (which may be a hashvalue of the hash function). The time-sensitive code may be anauthentication code that is available for a limited amount of time(e.g., 10 minutes, 30 minutes, and/or the like) to authenticate theuser. Accordingly, the user device (e.g., via the application) may beconfigured to receive a request associated with authenticating a userassociated with the user device, prompt the user for personalinformation (e.g., one or more specific pieces of personal informationrequested by the authentication platform), receive a user input that isto be representative of the requested personal information, generate anauthentication code based on the received user input, and provide theauthentication code to the authentication platform to permit theauthentication platform to authenticate the user.

According to some implementations, the authentication platform may useencryption when sending the authentication notification to the userdevice. For example, the user device (e.g., via the application) may beconfigured to receive the authentication notification using a publickey/private key pair. For example, the user device (and/or application)may receive and/or be associated with a private key when the applicationis downloaded and/or installed on the user device, when the userregisters an account (e.g., the account associated with the entity)—withthe application, and/or the like. The user device may then receive anauthentication notification, which is encrypted with a public keyassociated with the user device, and use the private key to decrypt theauthentication notification. Accordingly, an added layer of security canbe applied when requesting the user device to prompt the user for thepersonal information. As described herein, the authentication codegenerated by the user device (and/or the application of the user device)based on the user input may be compared to an authentication codegenerated by the authentication platform to authenticate the user.

The authentication platform may receive, from the user device, theauthentication code associated with a user input via a differentcommunication interface than the communication interface used in thecommunication between the user and the service platform and/or servicerepresentative. In some implementations, the authentication code may bereceived from the user device via a same communication interface used tosend the authentication notification. Accordingly, the authenticationplatform may provide out-of-band authentication relative to thecommunication between the user and the service platform and/or betweenthe user and the service representative.

In this way, the authentication platform may receive an authenticationcode from the user device to permit the authentication platform toauthenticate the user based on a user input used to generate theauthentication code. Accordingly, the authentication platform mayreceive the authentication code without the user having to communicatethe authentication code to the service representative, which may avoidhuman error in communicating the authentication code (e.g., if theservice representative mishears the user).

As further shown in FIG. 1B, and by reference number 150, theauthentication platform generates an authentication code based on thesame personal information that was requested from the user. Furthermore,the authentication platform may generate the authentication code using asame code generation process (e.g., using a same hash function, a sameinput to the hash function (e.g., same time-sensitive code), and/or thelike).

In some implementations, the authentication platform may obtain thepersonal information (e.g., the one or more pieces of personalinformation) that was requested from the user via the authenticationnotification. As mentioned above, the personal information may be storedin a data structure in association with the account identified via thecommunication. For example, assuming the user indicated that the user isassociated with Account 1234 (e.g., the user indicated that the user'sname was John Doe, the user provided the account number 1234, theservice platform identified the phone number, and/or the like), as shownin FIG. 1B, the authentication platform may obtain personal informationassociated with Account 1234. The pieces of personal information, thatare available for the authentication platform to authenticate the userand enable access to Account 1234, include the name, address, ID number,phone number, date of birth, and a favorite food. Accordingly, theauthentication platform may use one or more of the pieces of personalinformation to authenticate the user.

As described herein, the authentication platform may generate (e.g.,using a code generator) an authentication code based on the personalinformation. For example, the authentication platform may use thepersonal information in a hash function to generate the authenticationcode (which may be a hash value of the personal information). Accordingto the hash function, the authentication platform may hash the personalinformation with a time-sensitive code (e.g., a same time-sensitive codethat was provided in the authentication notification) to generate theauthentication code. In some implementations, the authenticationplatform may use the personal information to hash the time-sensitivecode to generate the authentication code. The time-sensitive code may beany code that is configured to expire after a threshold time period(e.g., relative to being generated, activated, and/or the like). Forexample, the time-sensitive code may be configured to only enable thehash function to generate the authentication code within a thresholdtime period (e.g., within 5 minutes, 10 minutes, an hour, and/or thelike) of sending the authentication notification, and after thethreshold time period expires, the hash function cannot generate theauthentication code (e.g., because the time-sensitive code is voided).In some implementations, the time-sensitive code is a randomly generatedcode. Expiration of the time-sensitive code may be monitored and/ortracked using expiration information that is stored in a data structureassociated with the authentication platform.

As described herein, the authentication platform may provide, to theuser device and in the authentication notification, the hash function,information indicating which personal information is to be requestedfrom the user, the time-sensitive code, and/or instructions to generatethe authentication code to permit the user device to generate theauthentication code based on the user input, such that theauthentication code generated by the authentication platform would matchthe authentication code generated by the user device if the user inputsthe correct personal information. Accordingly, to authenticate the user,the authentication platform may compare the authentication code that isgenerated from the user input by the user device with the authenticationcode generated from the personal information associated with the accountby the authentication platform. Following that comparison, the serviceplatform may authenticate the user based on whether the authenticationcodes match.

As described herein, the authentication codes may be considered secureauthentication codes in that the authentication codes are separatelygenerated from separate inputs (the user input received based on therequest for the personal information and the stored personalinformation). The separate authentication codes may indicate whether ornot the user is to be authenticated because the authentication codegenerated by the authentication platform was generated from the samepersonal information that was requested from the user to enable theauthentication code to be generated by the user device. Therefore, ifthe authentication codes do not match, the authentication platform candetermine that the user did not provide personal information thatmatches the stored personal information, and thus is likely anunauthorized user. Furthermore, if the authentication codes do match,the authentication platform can determine that the user did providepersonal information that matches the stored personal information, andthus, the user is likely an authorized user.

In this way, the authentication platform may determine whether the useris authenticated, in order to permit the service representative tocommunicate with the user (e.g., if the user is authenticated) or toprevent the service representative from communicating with the user(e.g., if the user is not authenticated).

As further shown in FIG. 1B, and by reference number 160 a, theauthentication platform indicates whether the user is authenticated tothe service representative. For example, the authentication platform maysend a message (e.g., a verification message that the user isauthenticated or a non-verification message that the user is notauthenticated) and/or a notification that can be presented to theservice representative via the service representative device.Additionally, or alternatively, the authentication platform may send amessage and/or notification to the user (e.g., to the user device)indicating that the user has been authenticated and/or that anauthorized access to the account is ongoing. In some cases, if the useris, in fact, a fraudulent user but was authenticated as describedherein, the notification to a customer associated with the account mayindicate to the customer that the fraudulent user accessed the accountvia the service platform or the service representative).

In some implementations, if the authentication platform determines thatthe user is authenticated (e.g., the authentication codes match), theauthentication platform may set up a communication interface between theuser and the service representative. For example, the authenticationplatform may cause the service platform to forward a call to the servicerepresentative to permit the user to communicate with the servicerepresentative. Additionally, or alternatively, the authenticationplatform may cause the service platform to open a chat interface on theservice representative device to permit the service representative tocommunicate with the user. Accordingly, if the communication interfacebetween the service platform and the user is a first communicationinterface, the authentication platform may cause or enable a secondcommunication interface to be established between the user and theservice representative.

In some implementations, if the authentication platform determines thatthe user is not authenticated (e.g., the authentication codes do notmatch), the authentication platform may perform one or more actions toprevent the user from accessing the account. For example, theauthentication platform may prevent the user from discussing the accountwith the service representative (e.g., by ending the communicationbetween the user and the service representative, by disconnecting theuser from the service platform, and/or the like). In someimplementations, the authentication platform may cause the serviceplatform to notify the user via the communication (e.g., using anautomated message) that the user failed the authentication process, thatthe user is not authorized to access the account, that the user is notauthorized to communicate with a service representative, and/or thelike. In some implementations, if the user fails a first authenticationprocess, as described herein, the authentication platform may permit theuser to undergo a second authentication process to authenticate theuser. In such cases, the authentication platform may automaticallyenable the user to undergo a threshold number of authenticationprocesses until the user is disconnected from the service platform. Insome implementations, if the user is not authenticated, theauthentication platform may cause the account identified by the user tobe flagged as the subject of fraudulent activity, may freeze fundsassociated with the account, may notify a customer associated with theaccount that an unauthorized access or a potential fraudulent access tothe customer's account was attempted, and/or the like.

In this way, the authentication platform may indicate to the servicerepresentative, the entity, and/or a user associated with the accountwhether the user was authenticated to permit the user to interact withthe service representative regarding an account or prevent the user fromaccessing the account.

As shown in FIG. 1C, and by reference number 140 b, the user providesthe authentication code that is generated by the user device based onthe user input associated with the personal information request (e.g.,based on the requested personal information in the authenticationnotification). For example, the user device, application, and/orauthentication function may be configured to generate the authenticationcode, as described herein, and present the authentication code to theuser via the user interface (e.g., a display device) of the user device.Accordingly, the user may read the authentication code, presented viathe user interface, and communicate the authentication code to theservice representative. In this way, network resources associated withthe user device sending the authentication code to the authenticationplatform can be conserved.

In some implementations, the service representative may request (e.g.,via the communication) that the user provide the authentication code tothe service representative. For example, based on determining that theuser is communicating with the authentication platform, theauthentication platform may send a message to or prompt the servicerepresentative that indicates that the service representative is torequest the user to read the authentication code to the servicerepresentative. Accordingly, the service representative maycorrespondingly request that the user provide the authentication code tothe service representative to permit the service representative (and/orauthentication platform) to authenticate the user. Additionally, oralternatively, the service representative, before requesting theauthentication code, may provide instructions to the user to assist theuser with entering the requested personal information into the userdevice (e.g., via the application and/or authentication function).Accordingly, the service representative may communicate with the user,according to instructions from the authentication platform, to assistthe user with entering a user input associated with requested personalinformation to enable the user device to generate the authenticationcode, as described herein.

In this way, the authentication platform may prompt the servicerepresentative to obtain the authentication code from the user, and theservice representative may receive the authentication code from the userto permit the service representative and/or the authentication platformto authenticate the user.

As further shown in FIG. 1C, and by reference number 150, theauthentication platform may generate the authentication code based onthe same personal information in a similar manner as described above inconnection with FIG. 1B.

In some implementations, the authentication platform may receive theauthentication code that was generated by the user device based on theuser input from the service representative device (rather than from theuser device as described above in connection with FIG. 1B). In someimplementations, the service representative device may be configured toreceive an authentication code via a user input from the servicerepresentative. For example, the service representative may enter theauthentication code that was generated by the user device based on theuser input from the user (e.g., the authentication code is presented tothe user, and the user provides the authentication code to the servicerepresentative) and communicated to the service representative. Theservice representative device may forward the authentication code to theauthentication platform to permit the authentication platform todetermine whether or not the user is to be authenticated as describedherein (e.g., based on whether the authentication code received from theservice representative device matches the authentication code generatedby the authentication platform).

As further shown in FIG. 1C, and by reference number 160 b, theauthentication platform provides the authentication code that wasgenerated from the stored personal information. For example, theauthentication platform may send the authentication code in a message tothe service representative device to permit the service representativedevice to present the authentication code via a user interface of theservice representative device. Accordingly, the service representativemay have access to both the authentication code generated by theauthentication platform and the authentication code generated by theuser device (e.g., as received from the user via the communication).Accordingly, the service representative may have the necessaryinformation (e.g., both authentication codes) to determine whether ornot to authenticate the user. The service representative may compare theauthentication codes and if they match, authenticate the user, andfurther engage in the communication with the user to permit the user toaccess the account. On the other hand, if the service representativedetermines that the access codes do not match, the servicerepresentative may indicate that the service representative cannotcommunicate with the user any further regarding the account, as the userwas not authenticated.

In some implementations, the hash function and/or the time-sensitivecode may be configured to convert the personal information and/or theuser input into a value having a same fixed length. For example, thehash functions and/or time-sensitive codes used by the authenticationfunction and/or authentication platform to generate the authenticationcodes may be configured to generate a four-digit number or characterstring, a six-digit number or character string, a nine-digit number orcharacter string, and/or the like. Accordingly, when comparing theauthentication code received from the user and the authentication codereceived from the authentication platform, the service representativemay quickly determine whether the authentication codes match (e.g.,rather than having to find a difference in a lengthy string of numbersand/or characters). Additionally, or alternatively, the authenticationplatform and/or user device (and application and/or authenticationfunction) may be configured to only provide a certain portion of theauthentication code to the service representative and the user,respectively. For example, the authentication platform may provide thelast four, eight, twelve, and/or the like digits or characters of theauthentication code generated by the authentication platform to theservice representative, and the user device may provide thecorresponding number of digits and/or characters of the authenticationcode generated by the user device to the user.

Accordingly, the service representative may be able to authenticate theuser by personally comparing the authentication codes generated by theauthentication platform and the user device. In this way, the userdevice, by presenting the respective authentication code to the user,may conserve network resources associated with sending theauthentication code to the authentication platform, and theauthentication platform may conserve computing resources associated withcomparing the two authentication codes to authenticate the user.

As indicated above, FIGS. 1A-1C are provided merely as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1C.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,environment 200 may include an authentication platform 210, a computingresource 215, a cloud computing environment 220, a user device 230, aservice representative device 240, a service platform 250, and a network260. Devices of environment 200 may interconnect via wired connections,wireless connections, or a combination of wired and wirelessconnections.

Authentication platform 210 includes one or more computing resourcesassigned to perform secure authentication of a user. For example,authentication platform 210 may be a platform implemented by cloudcomputing environment 220 that may obtain, from a user device, anauthentication code (e.g., from user device 230) generated based on userinput received in response to a request for personal information from auser, generate an authentication code based on corresponding storedpersonal information, determine whether the user is authenticated basedon the authentication code generated by and obtained from the userdevice and the authentication code generated by the authenticationplatform, provide (e.g., to service representative device 240) anindication of whether the user is authenticated, and/or the like. Insome implementations, the authentication platform 210 is implemented bycomputing resources 215 of cloud computing environment 220.

Authentication platform 210 may include a server device or a group ofserver devices. In some implementations, authentication platform 210 maybe hosted in the cloud computing environment 220. Notably, whileimplementations described herein describe authentication platform 210 asbeing hosted in cloud computing environment 220, in someimplementations, the authentication platform 210 may be non-cloud-basedor may be partially cloud-based.

Cloud computing environment 220 includes an environment that deliverscomputing as a service, whereby shared resources, services, etc., may beprovided to user device 230, service representative device 240, serviceplatform 250, and/or the like. Cloud computing environment 220 mayprovide computation, software, data access, storage, and/or otherservices that do not require end-user knowledge of a physical locationand configuration of a system and/or a device that delivers theservices. As shown, cloud computing environment 220 may includeauthentication platform 210 and computing resource 215.

Computing resource 215 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource215 may host authentication platform 210. The cloud resources mayinclude compute instances executing in computing resource 215, storagedevices provided in computing resource 215, data transfer devicesprovided by computing resource 215, etc. In some implementations,computing resource 215 may communicate with other computing resources215 via wired connections, wireless connections, or a combination ofwired and wireless connections.

As further shown in FIG. 2, computing resource 215 may include a groupof cloud resources, such as one or more applications (“APPs”) 215-1, oneor more virtual machines (“VMs”) 215-2, virtualized storage (“VSs”)215-3, one or more hypervisors (“HYPs”) 215-4, or the like.

Application 215-1 includes one or more software applications that may beprovided to or accessed by user device 230. Application 215-1 mayeliminate a need to install and execute the software applications onuser device 230. For example, application 215-1 may include softwareassociated with authentication platform 210 and/or any other softwarecapable of being provided via cloud computing environment 220. In someimplementations, one application 215-1 may send/receive informationto/from one or more other applications 215-1, via virtual machine 215-2.

Virtual machine 215-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 215-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 215-2. A system virtual machinemay provide a complete system platform that supports the execution of acomplete operating system (“OS”). A process virtual machine may executea single program and may support a single process. In someimplementations, virtual machine 215-2 may execute on behalf of a user(e.g., user device 230), and may manage the infrastructure of a cloudcomputing environment 220, such as data management, synchronization, orlong-duration data transfers.

Virtualized storage 215-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 215. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 215-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 215.Hypervisor 215-4 may present a virtual operating platform to the guestoperating systems and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

User device 230 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a user contacting a service representative of an entity (e.g., viaservice representative device 240) regarding an account maintained bythe entity. For example, user device 230 may include a communicationand/or computing device, such as a mobile phone (e.g., a smart phone, aradiotelephone, etc.), a laptop computer, a tablet computer, a handheldcomputer, a gaming device, a wearable communication device (e.g., asmart wristwatch, a pair of smart eyeglasses, etc.), a telephone, or asimilar type of device.

Service representative device 240 includes one or more devices capableof receiving, generating, storing, processing, and/or providinginformation associated with a service representative of an entity. Forexample, service representative device 240 may include a communicationand/or computing device, such as a mobile phone (e.g., a smart phone, aradiotelephone, etc.), a laptop computer, a tablet computer, a handheldcomputer, a wearable communication device (e.g., a smart wristwatch, apair of smart eyeglasses, etc.), a telephone, or a similar type ofdevice. In some implementations, the service representative may request,via service representative device 240, the user to enter the personalinformation to authenticate the user. In some implementations, servicerepresentative device 240 may be configured to receive an authenticationcode via a user input from the service representative. In someimplementations, service representative device 240 may receive (e.g.,from authentication platform 210) an indication of whether the user isauthenticated and/or be configured to present an indication of whetherthe user is authenticated. In some implementations, servicerepresentative device 240 may forward the authentication code toauthentication platform 210 to permit the authentication platform todetermine whether or not the user is to be authenticated.

Service platform 250 includes a server device (e.g., a host server, aweb server, an application server, etc.), a data center device, or asimilar device. In some implementations, the user may engage in acommunication with service platform 250. In some implementations,service platform 250 may perform one or more operations to identify theuser (e.g., when the user initiates the communication). In someimplementations, service platform 250 may request the user to indicate apurpose for the communication (e.g., to pay a bill, to dispute a bill,to engage in a transaction, to apply for a loan, to order a serviceand/or good, and/or the like).

Network 260 includes one or more wired and/or wireless networks. Forexample, network 260 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to authentication platform 210, computing resource 215,user device 230, service representative device 240, and/or serviceplatform 250. In some implementations, the authentication platform 210,computing resource 215, user device 230, service representative device240, and/or service platform 250 may include one or more devices 300and/or one or more components of device 300. As shown in FIG. 3, device300 may include a bus 310, a processor 320, a memory 330, a storagecomponent 340, an input component 350, an output component 360, and acommunication interface 370.

Bus 310 includes a component that permits communication among componentsof device 300. Processor 320 is implemented in hardware, firmware,and/or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read-onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for secureauthentication of a user. In some implementations, one or more processblocks of FIG. 4 may be performed by an authentication platform (e.g.,authentication platform 210). In some implementations, one or moreprocess blocks of FIG. 4 may be performed by another device or a groupof devices separate from or including the authentication platform, suchas a computing resource (e.g., computing resource 215), a user device(e.g., user device 230), a service representative device (e.g., servicerepresentative device 240), and a service platform (e.g., serviceplatform 250).

As shown in FIG. 4, process 400 may include detecting a communication toa call service center, wherein the communication is between a userdevice associated with a user and a service representative deviceassociated with the call service center (block 410). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may detect a communicationto a call service center, as described above. In some implementations,the communication is between a user device associated with a user and aservice representative device associated with the call service center.

As further shown in FIG. 4, process 400 may include providing, to theuser device, an authentication notification to request a firstauthentication code, wherein the authentication notification causes anauthentication application to launch on the user device, wherein theauthentication application generates the first authentication code byhashing a user input with a time-sensitive code, and wherein the userinput is received by the authentication application from the user via auser interface of the user device in association with a request that theuser provides one or more pieces of personal information (block 420).For example, the authentication platform (e.g., using computing resource215, processor 320, memory 330, storage component 340, output component360, communication interface 370, and/or the like) may provide, to theuser device, an authentication notification to request a firstauthentication code, as described above. In some implementations, theauthentication notification causes an authentication application tolaunch on the user device. In some implementations, the authenticationapplication generates the first authentication code by hashing a userinput with a time-sensitive code. In some implementations, the userinput is received by the authentication application from the user via auser interface of the user device in association with a request that theuser provides one or more pieces of personal information.

As shown in FIG. 4, process 400 may include receiving the firstauthentication code (block 430). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,the storage component 340, input component 350, communication interface370, and/or the like) may receive the first authentication code, asdescribed above.

As shown in FIG. 4, process 400 may include generating a secondauthentication code, wherein generating the second authentication codeincludes obtaining the one or more pieces of personal information,corresponding to the authentication request, from a data structure, andhashing the one or more pieces of personal information with thetime-sensitive code to generate the second authentication code (block440). For example, the authentication platform (e.g., using computingresource 215, processor 320, memory 330, storage component 340, and/orthe like) may generate a second authentication code, as described above.In some implementations, generating the second authentication codeincludes obtaining the one or more pieces of personal information,corresponding to the authentication request, from a data structure, andhashing the one or more pieces of personal information with thetime-sensitive code to generate the second authentication code.

As shown in FIG. 4, process 400 may include performing an action basedon whether the first authentication code matches the secondauthentication code (block 450). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may perform an actionbased on whether the first authentication code matches the secondauthentication code, as described above.

Process 400 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the quantity of pieces of information that isused for the first authentication code and the second authenticationcode may be based on a context of the communication. In someimplementations, the authentication notification may cause theauthentication application to be downloaded and installed on the userdevice before the authentication application is launched on the userdevice.

In some implementations, the authentication application may provide thefirst authentication code based on a request received from the servicerepresentative device. In some implementations, the one or more piecesof personal information may not be provided by the user device to theservice representative device to authenticate the user.

In some implementations, the first authentication code is received fromat least one of the user device, or the service representative device,where the service representative device is configured to receive thefirst authentication code via a second user input from the servicerepresentative, and where the user communicates, using the user device,the first authentication code to the service representative via thecommunication to permit the service representative to enter the seconduser input.

In some implementations, the authentication platform may send averification message to a service representative device, associated withthe service representative, to indicate that the user is authenticatedwhen the first authentication code matches the second authenticationcode, and may send a non-verification message to the servicerepresentative device, associated with the service representative, toindicate that the user is not authenticated when the firstauthentication code does not match the second authentication code

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for secureauthentication of a user. In some implementations, one or more processblocks of FIG. 5 may be performed by an authentication platform (e.g.,authentication platform 210). In some implementations, one or moreprocess blocks of FIG. 5 may be performed by another device or a groupof devices separate from or including an authentication platform (e.g.,authentication platform 210), such as a computing resource (e.g.,computing resource 215), a user device (e.g., user device 230), aservice representative device (e.g., service representative device 240),and a service platform (e.g., service platform 250).

As shown in FIG. 5, process 500 may include detecting a communicationinvolving a service representative and a user associated with an account(block 510). For example, the authentication platform (e.g., usingcomputing resource 215, processor 320, memory 330, storage component340, input component 350, communication interface 370, and/or the like)may detect a communication involving a service representative and a userassociated with an account, as described above.

As further shown in FIG. 5, process 500 may include sending anauthentication notification to a user device that is associated with theaccount, wherein the authentication notification causes the user deviceto display, via a user interface of the user device, an authenticationfield for the user (block 520). For example, the authentication platform(e.g., using computing resource 215, processor 320, memory 330, storagecomponent 340, output component 360, communication interface 370, and/orthe like) may send an authentication notification to a user device thatis associated with the account, as described above. In someimplementations, the authentication notification causes the user deviceto display, via a user interface of the user device, an authenticationfield for the user.

As further shown in FIG. 5, process 500 may include sending a message toa service representative device that is associated with the servicerepresentative, wherein the message indicates that the servicerepresentative is to request, via the communication, the user to enterpersonal information associated with the user into the authenticationfield, wherein the user device is configured to generate a firstauthentication code based on a user input received, via the userinterface of the user device, in the authentication field (block 530).For example, the authentication platform (e.g., using computing resource215, processor 320, memory 330, storage component 340, output component360, communication interface 370 and/or the like) may send a message toa service representative device that is associated with the servicerepresentative, as described above. In some implementations, the messageindicates that the service representative is to request, via thecommunication, the user to enter personal information associated withthe user into the authentication field. In some implementations, theuser device is configured to generate a first authentication code basedon a user input received, via the user interface of the user device, inthe authentication field.

As further shown in FIG. 5, process 500 may include generating a secondauthentication code based on personal information associated with theaccount from a data structure (block 540). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, and/or the like) may generate asecond authentication code based on personal information associated withthe account from a data structure, as described above.

As further shown in FIG. 5, process 500 may include receiving the firstauthentication code (block 550). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,storage component 340, input component 350, communication interface 370,and/or the like) may receive the first authentication code, as describedabove.

As further shown in FIG. 5, process 500 may include performing an actionbased on the first authentication code and the second authenticationcode (block 560). For example, the authentication platform (e.g., usingcomputing resource 215, processor 320, memory 330, storage component340, input component 350, output component 360, communication interface370, and/or the like) may perform an action based on the firstauthentication code and the second authentication code, as describedabove.

Process 500 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, when sending the authentication notification,the authentication platform may send the authentication notification tobe received, by the user device, via an authentication applicationinstalled on the user device, where the account is registered with theauthentication application, and where the authentication field is afield of the authentication application that is prompted after the userlogs in to the authentication application using at least one of a loginassociated with the account or a login associated with the user.

In some implementations, a previous communication an authorized userassociated with the account, an authorized user providing the personalinformation when registering the account, or an authorized user updatingthe personal information in the account.

In some implementations, when generating the second authentication code,the authentication platform may generate the second authentication codeusing a hash function, where the hash function hashes a time-sensitivecode with the personal information associated with the account, andwhere the hash function and the time-sensitive code are provided to theuser device in the authentication notification to permit the user deviceto correspondingly generate the first authentication code using the hashfunction and the time-sensitive code.

In some implementations, when receiving the first authentication code,the authentication platform may receive the first authentication codefrom the service representative device, where the service representativedevice is configured to receive the first authentication code via a userinput from the service representative, and where the message indicatesthat the service representative is to request, via the communication,the user to communicate the first authentication code to the servicerepresentative via the communication.

In some implementations, the authentication platform may determine thatthe first authentication code matches the second authentication code,where the message is a first message, and where the authenticationplatform, when performing the action, may send a second message to theservice representative device to indicate that the user is determined tobe an authorized user of the account to permit the user to furthercommunicate with the service representative.

In some implementations, the authentication platform may determine thatthe first authentication code does not match the second authenticationcode, where the message is a first message, and where the authenticationplatform, when performing the action, may send a second message to theservice representative device to indicate that the user is determined tobe an unauthorized user, and/or flag the account to indicate that anunauthorized access to the account was attempted.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for secureauthentication of a user. In some implementations, one or more processblocks of FIG. 6 may be performed by an authentication platform (e.g.,authentication platform 210). In some implementations, one or moreprocess blocks of FIG. 6 may be performed by another device or a groupof devices separate from or including an authentication platform (e.g.,authentication platform 210), such as a computing resource (e.g.,computing resource 215), a user device (e.g., user device 230), aservice representative device (e.g., service representative device 240),and a service platform (e.g., service platform 250).

As shown in FIG. 6, process 600 may include identifying an accountassociated with a user, wherein the account is identified based oninformation received via a first communication interface associated witha service platform (block 610). For example, the authentication platform(e.g., using computing resource 215, processor 320, memory 330, storagecomponent 340, input component 350, communication interface 370, and/orthe like) may identify an account associated with a user, as describedabove. In some implementations, the account is identified based oninformation received via a first communication interface associated witha service platform.

As further shown in FIG. 6, process 600 may include obtaining personalinformation associated with the account (block 620). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may obtain personalinformation associated with the account, as described above.

As shown in FIG. 6, process 600 may include sending an authenticationnotification to a user device associated with the user, wherein theauthentication notification prompts the user to enter the personalinformation via a user interface of the user device to permit the userdevice to generate a first authentication code (block 630). For example,the authentication platform (e.g., using computing resource 215,processor 320, memory 330, storage component 340, output component 360,communication interface 370, and/or the like) may send an authenticationnotification to a user device associated with the user, as describedabove. In some implementations, the authentication notification promptsthe user to enter the personal information via a user interface of theuser device to permit the user device to generate a first authenticationcode.

As further shown in FIG. 6, process 600 may include receiving the firstauthentication code from the user device (block 640). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may receive the firstauthentication code from the user device, as described above.

As further shown in FIG. 6, process 600 may include comparing the firstauthentication code and a second authentication code generated based onthe personal information (block 650). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,storage component 340, and/or the like) may compare the firstauthentication code and a second authentication code generated based onthe personal information, as described above.

As further shown in FIG. 6, process 600 may include performing an actionbased on the first authentication code and the second authenticationcode (block 660). For example, the authentication platform (e.g., usingcomputing resource 215, processor 320, memory 330, storage component340, input component 350, output component 360, communication interface370, and/or the like) may perform an action based on the firstauthentication code and the second authentication code, as describedabove.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the personal information may be stored inassociation with the account before the user provided the identificationinformation.

In some implementations, the authentication platform may generate thesecond authentication code using a hash function, where the hashfunction hashes a time-sensitive code with the personal information, andwhere the hash function and the time-sensitive code are provided to theuser device in the authentication notification to permit the user deviceto correspondingly generate the first authentication code using the hashfunction and the time-sensitive code.

In some implementations, the authentication platform may determine thatthe first authentication code matches the second authentication code,where the one or more instructions, that cause the one or moreprocessors to perform the action, cause the one or more processors toset up a second communication interface between the user and a servicerepresentative based on the first authentication code matching thesecond authentication code.

In some implementations, the authentication platform may determine thatthe first authentication code does not match the second authenticationcode, where the one or more instructions, that cause the one or moreprocessors to perform the action, cause the one or more processors,based on determining that the first authentication code does not matchthe second authentication code, to indicate to the user, via the firstcommunication interface, that the user is not authorized to communicatewith the service platform, and/or to shut down the first communicationinterface.

In some implementations, the authentication notification may be sent viaa second communication interface and the first authentication code maybe received via the second communication interface. In someimplementations, the first communication interface and the secondcommunication interface are different communication interfaces.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIG. 7 is a flow chart of an example process 700 for secureauthentication of a user. In some implementations, one or more processblocks of FIG. 7 may be performed by an authentication platform (e.g.,authentication platform 210). In some implementations, one or moreprocess blocks of FIG. 7 may be performed by another device or a groupof devices separate from or including an authentication platform (e.g.,authentication platform 210), such as a computing resource (e.g.,computing resource 215), a user device (e.g., user device 230), aservice representative device (e.g., service representative device 240),and a service platform (e.g., service platform 250).

As shown in FIG. 7, process 700 may include detecting a communicationwith a user device of a user (block 710). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may detect a communicationwith a user device of a user, as described above.

As further shown in FIG. 7, process 700 may include providing, to theuser device, an authentication request, wherein the request causes anauthentication function to be presented on the user device, wherein theauthentication function is configured to generate a first authenticationcode by hashing a user input received in association with a request fora piece of personal information of a user, wherein the user input isreceived via a user interface of the user device (block 720). Forexample, the authentication platform (e.g., using computing resource215, processor 320, memory 330, storage component 340, output component360, communication interface 370, and/or the like) may provide, to theuser device, an authentication request, as described above. In someimplementations, the request causes an authentication application tolaunch on the user device. In some implementations, the request causesan authentication function to be presented on the user device. In someimplementations, the authentication function is configured to generate afirst authentication code by hashing a user input received inassociation with a request for a piece of personal information of auser. In some implementations, the user input is received via a userinterface of the user device.

As further shown in FIG. 7, process 700 may include receiving the firstauthentication code from the user device (block 730). For example, theauthentication platform (e.g., using computing resource 215, processor320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may receive the firstauthentication code from the user device, as described above.

As further shown in FIG. 7, process 700 may include generating a secondauthentication code, wherein generating the second authentication codecomprises obtaining the piece of personal information from a datastructure, and hashing the piece of personal information to generate thesecond authentication code (block 740). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,storage component 340, and/or the like) may generate a secondauthentication code, as described above. In some implementations,generating the second authentication code comprises obtaining the pieceof personal information from a data structure, and hashing the piece ofpersonal information to generate the second authentication code.

As further shown in FIG. 7, process 700 may include authenticating theuser based on the first authentication code matching the secondauthentication code (block 750). For example, the authenticationplatform (e.g., using computing resource 215, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may authenticate the userbased on the first authentication code matching the secondauthentication code, as described above.

Process 700 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

Although FIG. 7 shows example blocks of process 700, in someimplementations, process 700 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 7. Additionally, or alternatively, two or more of theblocks of process 700 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, or the like.A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom an authentication platform, authentication notification associatedwith an account; generating, by the device and based on receiving theauthentication notification, a first authentication code using a hashfunction, wherein the hash function hashes a time-sensitive code withfirst information associated with the account, and wherein theauthentication notification includes at least one of the hash functionor the time-sensitive code to permit generating the first authenticationcode based on the hash function and the time-sensitive code; receiving,by the device, from the authentication platform, and based on the devicereceiving the authentication notification, a second authentication code,wherein the second authentication code is generated based on secondinformation associated with the account; comparing, by the device, thefirst authentication code and the second authentication code; andperforming, by the device, an action based on whether the firstauthentication code matches the second authentication code.
 2. Themethod of claim 1, wherein the authentication notification is receivedvia a first communication interface with a service platform, and whereinthe action includes configuring a second communication interface forcommunication with another device.
 3. The method of claim 1, furthercomprising: installing, based on receiving the authenticationnotification, an application; and receiving, via the application, thefirst information, wherein the first authentication code is generatedvia the application.
 4. The method of claim 1, wherein the firstauthentication code is generated based on a request received from aservice representative device.
 5. The method of claim 1, furthercomprising: installing, based on receiving the authenticationnotification, an application; receiving, via the application, the firstinformation, wherein the first authentication code is generated via theapplication; and obtaining, based on stored information associated withthe account, the second information.
 6. The method of claim 1, whereinthe action includes configuring a communication interface forcommunication with another device.
 7. The method of claim 1, wherein thefirst authentication code is provided via a first communicationinterface, and wherein the authentication notification is provided via asecond communication interface that is different from the firstcommunication interface.
 8. A device, comprising: one or more memories;and one or more processors, coupled to the one or more memories,configured to: receive, from an authentication platform, authenticationnotification associated with an account; generate, based on receivingthe authentication notification, a first authentication code using ahash function, wherein the hash function hashes a time-sensitive codewith first information associated with the account, and wherein theauthentication notification includes at least one of the hash functionor the time-sensitive code to permit generating the first authenticationcode based on the hash function and the time-sensitive code; receive,from the authentication platform, and based on the device receiving theauthentication notification, a second authentication code, wherein thesecond authentication code is generated based on second informationassociated with the account; compare the first authentication code andthe second authentication code; and perform an action based on whetherthe first authentication code matches the second authentication code. 9.The device of claim 8, wherein the authentication notification isreceived via a first communication interface with a service platform,and wherein the action includes configuring a second communicationinterface for communication with another device.
 10. The device of claim8, wherein the one or more processors are further configured to:install, based on receiving the authentication notification, anapplication; and receive, via the application, the first information,wherein the first authentication code is generated via the application.11. The device of claim 8, wherein the first authentication code isgenerated based on a request received from a service representativedevice.
 12. The device of claim 8, wherein the one or more processorsare further configured to: install, based on receiving theauthentication notification, an application; receive, via theapplication, the first information, wherein the first authenticationcode is generated via the application; and obtain, based on storedinformation associated with the account, the second information.
 13. Thedevice of claim 8, wherein the action includes configuring acommunication interface for communication with another device.
 14. Thedevice of claim 8, wherein the first authentication code is provided viaa first communication interface, and wherein the authenticationnotification is provided via a second communication interface that isdifferent from the first communication interface.
 15. A non-transitorycomputer-readable medium storing a set of instructions, the set ofinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the device to: receive, froman authentication platform, authentication notification associated withan account; generate, based on receiving the authenticationnotification, a first authentication code using a hash function, whereinthe hash function hashes a time-sensitive code with first informationassociated with the account, and wherein the authentication notificationincludes at least one of the hash function or the time-sensitive code topermit generating the first authentication code based on the hashfunction and the time-sensitive code; receive, from the authenticationplatform, and based on the device receiving the authenticationnotification, a second authentication code, wherein the secondauthentication code is generated based on second information associatedwith the account; compare the first authentication code and the secondauthentication code; and perform an action based on whether the firstauthentication code matches the second authentication code.
 16. Thenon-transitory computer-readable medium of claim 15, wherein theauthentication notification is received via a first communicationinterface with a service platform, and wherein the action includesconfiguring a second communication interface for communication withanother device.
 17. The non-transitory computer-readable medium of claim15, wherein the one or more instructions further cause the device to:install, based on receiving the authentication notification, anapplication; and receive, via the application, the first information,wherein the first authentication code is generated via the application.18. The non-transitory computer-readable medium of claim 15, wherein thefirst authentication code is generated based on a request received froma service representative device.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions further cause the device to: install, based on receivingthe authentication notification, an application; receive, via theapplication, the first information, wherein the first authenticationcode is generated via the application; and obtain, based on storedinformation associated with the account, the second information.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions further cause the device to configure a communicationinterface for communication with another device.